Restricting Buttons in DiveTab

Adding access control on a DiveTab button (associated with an area in the script) removes it from the menu for all users or groups without explicit access; administrators are the exception. These procedures demonstrate methods of restricting access, based on a group, to a button and all included content.

For example, assume a number of pages have been created for use at an upcoming retreat for the management staff. All pages have been defined in data-area Management Retreat. All users on the server have access to the DiveTab project. Users who are managers have been assigned to the Management group defined on the server. For more information, see Managing Groups.

To add security so only the managers can see the retreat materials, you can proceed in one of two ways.

Restricting Buttons Using the GUI

Right-click the project folder in the Explorer panel and select Edit Access Control.

The Access for / tab opens.
Verify that the File Access is properly set.
1. Click the File Access tab within the Access for / tab.
2. Click the Add icon (+), located on the upper right of the Read Permissions box.
  
  TIP: The default is to give read permission to all users. Select All Users in the Condition column to change to a Group, User, or Property, and fill in the Condition Details to change the Read Permissions.
Click the DiveTab Access tab within the Access for / tab.
Click the Add Areas… button next to Restrict Areas (0).

The Restrict Areas Editor dialog opens.
There are two methods to add areas:
- Click the Add icon (+) and type the area name in the new row. Repeat for as many areas as needed.
- Select a divetab file from the Search Results and then select the check boxes for the areas in the adjacent list where you want to restrict access.
  
  Click the Add selected areas to restricted areas list button to add them to the Restricted Areas list. This method is a best practice.
NOTE: To remove these areas, select one or more areas under the Restricted Areas section and select the Remove icon (-). A confirmation pop-up window appears; click Yes to delete the rows or No to cancel.
Click the Add selected areas to restricted areas list button.
Click the Keep changes and close editor button.

The Restrict Areas Editor closes. The restricted areas appear, listed to the right of the Edit... button.
Click the Add (+) icon, located in the top right of the Add Areas Rule box.

A new rule row appears.
Select Group from the pull-down menu under the Condition column.

TIP: Click the Condition Details column to reflect the chosen condition.
Under the Condition Details column, use the pull-down menu on the left to select the group (Management). You can list specific areas under the Areas column.
Save the Access for / tab.

Restricting Buttons Using the Code

Right-click the project folder in the Explorer panel and select Edit Access Control.

The Access for / tab opens.
Click the Script tab within Access for / tab.

The code opens.
Make sure the file-access is set. That is, this file has default content that you can comment or uncomment as a starting point. For example:
Start a divetab-access block within the access block.
Add a tag for restrict-areas and include the area id Management Retreat. For example:
```
  divetab-access { 
    restrict-areas "Management Retreat" 
  } 
```

Add an allow-area block with an if-group clause for the group Management. For example:

  divetab-access { 
    restrict-areas "Management Retreat" 
    allow-area "Management Retreat" { 
      if-group "Management" 
    } 
  }

Save the Access for / tab.

Only users who are included in the Management group can see pages defined in the area with id Management Retreat.